capture generation after upload#718
Merged
martindurant merged 1 commit intofsspec:mainfrom Dec 15, 2025
Merged
Conversation
shcheklein
force-pushed
the
fix-capture-generation-on-write
branch
from
1010780 to
ac632c4
Compare
shcheklein
force-pushed
the
fix-capture-generation-on-write
branch
from
ac632c4 to
0190491
Compare
Contributor
Author
|
@martindurant do you know by chance who is maintaining the project and could release this change? |
Member
|
It is indeed me. gcsfs was released last week (2025.12.0), before I went on holiday. I will be working again next week. |
Contributor
Author
|
thanks @martindurant 🙏 , nw and no rush on this. |
Member
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To be able to refer to a file properly (in case multiple uploads happening simultaneously to the same path), we want to grab generation from the response. S3 already does this.
Azure - I'll take a look and also try to fix it.Azure: fsspec/adlfs#524